Skip to main content

This is a new service – your feedback will help us to improve it.

Royal Borough of Kensington and Chelsea

Article 4 direction area

There is a problem

  • 84 issue of type invalid category value

Article 4 - No 30

reference
14
name
Article 4 - No 30
article-4-direction
14
permitted-development-rights

undefined

Minor alterations in Conservation Areas including works to windows
uprns
address-texts
geometry
MULTIPOLYGON (((-0.211030 51.502060,-0.210230 51.502260,-0.210270 51.502300,-0.210350 51.502410,-0.210900 51.502260,-0.210930 51.502260,-0.211270 51.502170,-0.211260 51.502140,-0.211190 51.502050,-0.211180 51.502020,-0.211030 51.502060)),((-0.210960 51.502940,-0.211080 51.503090,-0.211460 51.502990,-0.211510 51.502970,-0.211760 51.502910,-0.211680 51.502780,-0.211660 51.502760,-0.211580 51.502630,-0.211480 51.502490,-0.211470 51.502460,-0.210590 51.502690,-0.210780 51.502900,-0.210900 51.502870,-0.210960 51.502940)),((-0.210100 51.500660,-0.209990 51.500700,-0.210050 51.500720,-0.210060 51.500730,-0.209990 51.500770,-0.209960 51.500800,-0.209850 51.500860,-0.209620 51.501010,-0.209940 51.501490,-0.210290 51.501370,-0.210680 51.501270,-0.210660 51.501250,-0.210460 51.500940,-0.210330 51.500760,-0.210250 51.500620,-0.210100 51.500660)))
point
POINT (-0.210638 51.501896)
notes
entry-date
2025-01-03
start-date
end-date

How to fix this issue

Your dataset is missing the permitted-development-rights column.

The Article 4 direction area guidance explains how to fix the issue:

permitted-development-rights

A list of the permitted development rights withdrawn by the article 4 direction.

Separate the rights in the list using semicolons.

Only use rights from our permitted development right dataset. If the area withdraws a permitted development right that is not in our dataset, email digitalland@communities.gov.uk.

Example: 3D;3M;11B

How to improve Royal Borough of Kensington and Chelsea’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL